This repository was archived by the owner on Oct 23, 2023. It is now read-only.
Handle recursion errors #330
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some cases, for example when a frame is App.ZApplication.ZApplicationWrapper, then "frame.f_locals.get('self', None)" raises a maximum recursion depth error. This fix catches these and moves further so Zope continues to run (without the fix Zope breaks) and we still get a (request-less) error report in Sentry.